Description

Fixes incorrect bound handling in the jemalloc stats callback (write_cb).

The callback previously used the buffer’s total capacity instead of the remaining space (capacity - len). This allowed the buffer to grow across multiple invocations, exceeding the intended limit and potentially triggering reallocation inside the callback, which is explicitly undesirable in this context.

This change ensures that each write is bounded by the remaining capacity. Once the buffer is full, the callback returns early and performs no further writes.

How Has This Been Tested?

• Added unit tests to verify:
  • Buffer length never exceeds its capacity across multiple callback invocations
  • No capacity growth occurs after the buffer is full
  • Incoming data is correctly truncated to remaining space
  • Zero-capacity edge case behaves as expected
• Verified behavior is deterministic and matches intended bounded-write semantics

Key Areas to Review

• write_cb logic:
  • Uses capacity - len (via saturating_sub) to compute remaining space
  • Returns early when no space is left
  • Copies only the allowed number of bytes per invocation
• Safety:
  • No changes to unsafe pointer usage or callback interface
  • No new allocations introduced in the callback path

Type of Change

• Bug fix

Which Components or Systems Does This Change Impact?

• Other (Admin Service)

Checklist

• I have read and followed the CONTRIBUTING doc
• I have performed a self-review of my own code
• I tested both happy and unhappy path of the functionality